-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split phase change from MirPass
#102340
Split phase change from MirPass
#102340
Conversation
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit b6bd3d8deae8ab0c97efacc73a53a932608d1c78 with merge 91f1e60cacbc612e315bf021ed4cf3dbd485dfcc... |
☀️ Try build successful - checks-actions |
Queued 91f1e60cacbc612e315bf021ed4cf3dbd485dfcc with parent de0b511, future comparison URL. |
Finished benchmarking commit (91f1e60cacbc612e315bf021ed4cf3dbd485dfcc): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Footnotes |
@@ -292,6 +319,7 @@ impl<'tcx> Body<'tcx> { | |||
|
|||
let mut body = Body { | |||
phase: MirPhase::Built, | |||
pass_count: 1, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That looks like pretty fragile initialization. Is this always 1 initially?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this is a counter that is always set/reset to 1 everywhere.
The revert is entirely a shot in the dark for getting the perf from #99102 back, but let's see (waiting on CI before queuing) |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 43ea3c1d6b34a9d562c2d72e3497c1c1e73ef65e with merge 43ae51f3bc0705a23cc4c354a410097b33a2ef65... |
☀️ Try build successful - checks-actions |
Queued 43ae51f3bc0705a23cc4c354a410097b33a2ef65 with parent d6734be, future comparison URL. |
Finished benchmarking commit (43ae51f3bc0705a23cc4c354a410097b33a2ef65): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Footnotes |
43ea3c1
to
be2401b
Compare
I've dropped the last commit (which turned out to not give back any perf benefits). I'll keep looking into fixing the perf regression from the other PR, but in the meantime I think we should probably merge this, since it's an improvement on its own. |
@bors r+ |
⌛ Testing commit be2401b with merge 051edf415cb5a12984d6976d7df4f50ed60e0bea... |
💥 Test timed out |
Was the failure spurious? How do I tell? |
@bors retry timeout Probably just an arbitrary spurious CI failure |
☀️ Test successful - checks-actions |
Finished benchmarking commit (bed4ad6): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Footnotes |
FYI using this commit to get a SMT + Turbo vs. non-SMT and non-Turbo comparison on the perf machine, expecting another post here as a result. See discussion here https://rust-lang.zulipchat.com/#narrow/stream/247081-t-compiler.2Fperformance/topic/Disabling.20hyperthreading.2Fturbo/near/306100379 |
Finished benchmarking commit (bed4ad6): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Footnotes |
…on, r=oli-obk Split phase change from `MirPass` The main goal here is to simplify the pass manager logic. `MirPass` no longer contains the `phase_change` method, and `run_passes` instead accepts an `Option<PhaseChange>`. The hope is that this addresses the comments (and maybe perf regression) from rust-lang#99102 . r? `@oli-obk` cc `@RalfJung`
The main goal here is to simplify the pass manager logic.
MirPass
no longer contains thephase_change
method, andrun_passes
instead accepts anOption<PhaseChange>
. The hope is that this addresses the comments (and maybe perf regression) from #99102 .r? @oli-obk cc @RalfJung